home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Stac Reachout 7
/
Stac Reachout 7.iso
/
STACFAX
/
8608.TXT
< prev
next >
Wrap
Text File
|
1997-01-31
|
6KB
|
125 lines
-----------------------------------------------------------------
STAC NOTE STAC NOTE
WINDOWS HANGS
(Applies to ReachOut version 5.X)
STAC FAX 8608 (9/95)
-----------------------------------------------------------------
BACKGROUND
In certain circumstances the startup of Windows may ôhangö. This
is usually caused by a conflict in the SYSTEM.INI file, a memory
or a video driver conflict.
SOLUTION
- Check/cleanup the SYSTEM.INI file.
- Check video resolution.
- Ensure there are no memory conflicts with Network Interface
Cards.
- Modify the GVx batch file if connecting DOS to DOS then
starting Windows.
- Obtain the ReachOut 5 Update file if using Netbios.
- Look for previous versions of the REACHOUT.INI file.
- Update a Novell DLL if running Windows from the network
server.
- Modify the SYSTEM.INI FILE if the Viewer displays "Windows
Loading...".
Check/cleanup the SYSTEM.INI file
1. If there is any possibility that another remote control
package has ever been installed on the system, clean out any
remnants of that installation from the SYSTEM.INI file.
StacFax 8604 provides examples of the types of entries that
some other remote control packages make, and what you may do
to restore the file to its original state.
2. If you have ever had ReachOut 3.x on the system, clean out
any lines left over in the SYSTEM.INI file. StacFax 8604 can
assist here also.
Check video resolution
In some cases setting a high video resolution, particularly with
leading-edge video cards may cause Windows to hang. These cards
sometimes skirt the rules on video display in order to achieve
better performance. Lower the video resolution to SVGA or VGA.
Ensure there are no memory conflicts with Network Interface Cards
Network Interface Cards (NIC) often require a specific memory
range. This range must be excluded from use by other devices.
Exclude the range in the Windows SYSTEM.INI file. In the [386Enh]
section add a line:
EMMExclude=paragraph-range
where paragraph-range is the memory address range to be excluded.
Consult the NIC documentation to determine the range to exclude.
Modify the GVx batch file if connecting DOS to DOS then starting
Windows
This problem is usually related to the video display. Add the
following switch to the end of the VIEWMDM or VIEWNET line in the
GVM or GVN batch file:
/SVGAMODE=<rax>, <rbx>
where rax, rbx are the hex address for the Viewer's video card
supervga mode. These values are found in the video card manual,
or Windows SYSTEM.INI.
Common values are:
DEC 52,0 NCR 58,0 Video7 6f05,62
Compaq 29,0 Oak 52,0 Western Dig. 58,0
Trident 5b,0 ATI 54,0 Paradise 58,0
Realtek 1f,0 Dell 6a,0 Orchid 6a,0
Diamond 6a,0 STB 29,0
If the appropriate value doesn't work, try /SVGAMODE=1.
Obtain the ReachOut 5 Update file if using Netbios
If you are using Windows for Workgroups and Netbios, along with
the ODI/NDIS communications driver, apply the ReachOut 5 Update
file. The file is RO5UP.EXE and is available from the Stac BBS at
(619) 794-3711. It is also available on the Stac forum on
CompuServ and from the Internet at ftp.stac.com. To use the file
simply place it in the REACHOUT directory and run it. Follow the
onscreen messages to complete the update.
Modify the SYSTEM.INI FILE if the Viewer displays "Windows
Loading..."
If the Viewer displays "Windows Loading..." but the Host actually
goes into Windows, add
device=c:\reachout\VRCHSYS.386
to the [386Enh] section of the Host's SYSTEM.INI file. Do this
even if you are not using the Windows Host. ReachOut needs the
driver to pass video signals to the Viewer.
Update a Novell DLL if running Windows from the network server
If the ReachOut Viewer is in DOS, and you attempt to open Windows
on the Host, it may hang if you are running Windows from the
server using either VLM's or NETX. This may be solved by updating
the Novell drivers. Obtain the file NWDLL2.EXE from Novell to
update the drivers. Consult Novell for directions on applying the
update.
Look for previous versions of the REACHOUT.INI file
If you previously installed ReachOut, the old REACHOUT.INI file
may have persisted in the some directory, such as the user's
network home directory. Delete the old REACHOUT.INI file.
-----------------------------------------------------------------
Copyright 1995 Stac Electronics
Information provided in this document is provided as is without
warranty of any kind either expressed or implied, including but
not limited to the implied warranties of merchantability and/or
fitness for a particular purpose. The user assumes the entire
risk as to the accuracy and use of this document.